Can Exchange 2003 Route OUTBOUND email based on the "FROM" address?xyz.com to smarthost1abc.com to smarthost2Thank you for your time in advance!!!

Yes, see here: The question is: Why do we need a SMTP Connector? The answer: You are connecting to a Microsoft Exchange Server 5.5 computer in another routing group (site), and want to use SMTP. You want to configure either server-side or client-side ETRN/TURN. You want either to send or not to send ETRN/TURN. You want to request ETRN/TURN when sending messages. You want to request ETRN/TURN from different servers. You want to configure outbound security, and to do it once and affect many outbound servers. You want to permit high, normal, or low message priorities for a domain. You want to permit system or non-system messages. You want to schedule the SMTP connector. You want to use different delivery times for oversized messages. You want to queue mail for remote triggered delivery. You want to send HELO instead of EHLO. You want to specify a specific address space. You want to set delivery restrictions. read this for more info: http://www.msexchange.org/tutorials/Configuring-SMTP-Connector.html

Mike,Thanks so much for taking the time to answer my post!!!I have tried and tried to route OUTBOUND mail (from within my organization) based on the domain name in the FROM: field.Joe@xyz.com to route to Smarthost_ONEandJoe@abc.com to route to Smarthost_TWO..but to no avail.Most (on other forums) have said that the address space is simply for INBOUND routing. The "delivery restrictions" dont seem to accomplish what I am looking for either.I have spent a week in my full blown lab and I am slowly but surely giving up on getting this accomplished. I believe a programmer can get this to work but I need to configure via the UI only.Have you (or anyone) actually seen this work?

Here is a response I received from a different forum:Anybody agree/disagree? "I believe so, however I think you need to engineer a transport event sink to meet this scenario (meaning there's no UI to configure this).This article delves into how to use C# to make an agent:http://support.microsoft.com/kb/894286Here's E2K3's transport events:http://msdn2.microsoft.com/en-us/library/ms528385.aspxI believe the IDNSResolverInterface can be utilized to override where a message is going to go, so you can set a smarthost value on the fly.I'd post to the extensibility forum to see if they can elaborate further..."

OK here is how to accomplish this:***IMPORTANT*****DO THIS AT YOUR OWN RISK - test in a lab first as we have done.This will not work for multiple domains for a single user.for example:This WILL NOT route out a specific connector:JOE@XYZ.COMJOE@ABC.COMbutThis WILL route out a specific connector:JOE@XYZ.COMJOE1@ABC.COMSo in this scenerio I want JOE@XYZ.COM to deliver out to the internet as usual and I want JOE1@ABC.COM to go to a special SMARTHOST1. Add (CheckConnectorRestrictions and set it to 1) DWORD registry entry to this key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Resvc\Parameters*note: we rebooted after this step2. Create Two (or more) SMTP Connectors (ADDRESS SPACE on both set to *, same cost is fine)3. On the SMTP connector (that will handle normal internet mail) click the "Delivery Restrictions" tab and set to:"By default, messages from everyone are: ACCEPTED"also click "ADD" under "Reject messages from:" and add JOE1@ABC.COM4. On the SMTP connector (that will handle mail you would like to forward to a special SMARTHOST) click the "Delivery Restrictions" tab and set to:"By default, messages from everyone are: REJECTED"also click "ADD" under "Accept messages from:" and add JOE1@ABC.COM5. Issue IISRESET from a command prompt